Fix/stale-applirank-env-vars#58
Conversation
…v.example Closes #57 - Add LIVE_DEMO_EMAIL=demo@reqcore.com — missing entirely from .env.example, meaning operators had no guidance when renaming the domain. Its absence let a stale DEMO_EMAIL=demo@applirank.com override the correct fallback. - Fix GITHUB_FEEDBACK_REPO example: reqcore/reqcore → reqcore-inc/reqcore Production env vars to update in Railway: LIVE_DEMO_EMAIL=demo@reqcore.com (was: missing) DEMO_ORG_SLUG=reqcore-demo (was: applirank-demo — also bypasses demo write-guard) GITHUB_FEEDBACK_REPO=reqcore-inc/reqcore (was: applirank/applirank) BETTER_AUTH_URL=https://reqcore.com (was: https://applirank.com)
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: defaults Review profile: CHILL Plan: Pro 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR introduces a runtime guard for the demo email configuration in Nuxt and adds legacy cleanup logic to the seed script. The config now validates the demo email against stale applirank.com domains, while the seed script removes any pre-existing legacy demo organization and user records before seeding. Changes
Possibly Related Issues
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Type of change
Validation
DCO
Signed-off-by) viagit commit -sSummary by CodeRabbit
Bug Fixes
Chores